Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 659202fa588f471a25e622656c4e06d45151dcde836463549c9c91b210206736

Tx prefix hash: cbe4ebea87ef846302531e5761ddd1f3aeff1672eb6d688cdb3a20d351700a16
Tx public key: b0b51d8d980083c1c03f23e765eba972cde9d15a9e6a25d55a66660b72f2bdf6
Timestamp: 1712264268 Timestamp [UCT]: 2024-04-04 20:57:48 Age [y:d:h:m:s]: 00:233:18:27:58
Block: 993408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167377 RingCT/type: yes/0
Extra: 01b0b51d8d980083c1c03f23e765eba972cde9d15a9e6a25d55a66660b72f2bdf602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 116a1fc9db3982458e5a0c89c90180112e35c80796c16e4c6bed4a8b9e93f4cf 0.600000000000 1453794 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 993418, "vin": [ { "gen": { "height": 993408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "116a1fc9db3982458e5a0c89c90180112e35c80796c16e4c6bed4a8b9e93f4cf" } } ], "extra": [ 1, 176, 181, 29, 141, 152, 0, 131, 193, 192, 63, 35, 231, 101, 235, 169, 114, 205, 233, 209, 90, 158, 106, 37, 213, 90, 102, 102, 11, 114, 242, 189, 246, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8