Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2addd76cad19d11183e437fdbd2d423192029521d72f3a81f89b6bdf67c3301d

Tx prefix hash: fe5161f284f196d7293e021bc6e2c1425b5d58f830999439bd246aa8fa1d5344
Tx public key: cf1a5158bcc3af8e71cdd926a81caf86e32695a9821f902c42ded40d6fee322f
Timestamp: 1726929121 Timestamp [UCT]: 2024-09-21 14:32:01 Age [y:d:h:m:s]: 00:263:06:16:08
Block: 1115004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187994 RingCT/type: yes/0
Extra: 01cf1a5158bcc3af8e71cdd926a81caf86e32695a9821f902c42ded40d6fee322f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f376602ce9f270323d5e7e9aad9d0116a6364bcf8e8b17149859666a6dd34b 0.600000000000 1594981 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": 1115014, "vin": [ { "gen": { "height": 1115004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f376602ce9f270323d5e7e9aad9d0116a6364bcf8e8b17149859666a6dd34b" } } ], "extra": [ 1, 207, 26, 81, 88, 188, 195, 175, 142, 113, 205, 217, 38, 168, 28, 175, 134, 227, 38, 149, 169, 130, 31, 144, 44, 66, 222, 212, 13, 111, 238, 50, 47, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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