Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf2d647bef3987ae8bebc6ee568c0a68cf134dc22a9ac2aac37b03db3590d19

Tx prefix hash: 7c6e4e536ddfd8e6895443f7bf7803a86c2d55f9b5d505ff10ade2107a30d207
Tx public key: 53db7cc17b8872e607eaa585d4d5c9346e9ce89094201c0fe5259fea46fee8b4
Timestamp: 1718134512 Timestamp [UCT]: 2024-06-11 19:35:12 Age [y:d:h:m:s]: 00:257:02:48:44
Block: 1042091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183707 RingCT/type: yes/0
Extra: 0153db7cc17b8872e607eaa585d4d5c9346e9ce89094201c0fe5259fea46fee8b40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ebdef98f5c6910b4279cac5457bdcc60196b52f20d4d74ed7cba68e676edd57 0.600000000000 1510926 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": 1042101, "vin": [ { "gen": { "height": 1042091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ebdef98f5c6910b4279cac5457bdcc60196b52f20d4d74ed7cba68e676edd57" } } ], "extra": [ 1, 83, 219, 124, 193, 123, 136, 114, 230, 7, 234, 165, 133, 212, 213, 201, 52, 110, 156, 232, 144, 148, 32, 28, 15, 229, 37, 159, 234, 70, 254, 232, 180, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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