Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd57caf3a3b421bef94d0f44e5f048710e7ab0a1d11f9c50fffeb7ac345ebf12

Tx prefix hash: 515f04363d074bc1673523964cac6d1a77f4454fcfe32a284e75afaa64b0521c
Tx public key: 30da2dbd0fce6db3b6a56152c7d66decbbdf9e7aeb1af174a699162bf619f832
Timestamp: 1726136491 Timestamp [UCT]: 2024-09-12 10:21:31 Age [y:d:h:m:s]: 00:245:10:59:02
Block: 1108427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175298 RingCT/type: yes/0
Extra: 0130da2dbd0fce6db3b6a56152c7d66decbbdf9e7aeb1af174a699162bf619f83202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2097799c4d736e3c76c4c38659115f178f4d0deb6487f39f3020a28a91652881 0.600000000000 1586318 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": 1108437, "vin": [ { "gen": { "height": 1108427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2097799c4d736e3c76c4c38659115f178f4d0deb6487f39f3020a28a91652881" } } ], "extra": [ 1, 48, 218, 45, 189, 15, 206, 109, 179, 182, 165, 97, 82, 199, 214, 109, 236, 187, 223, 158, 122, 235, 26, 241, 116, 166, 153, 22, 43, 246, 25, 248, 50, 2, 17, 0, 0, 0, 6, 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