Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0c294ceec0f84f41f155c0403afc5be800ce8d3220c0f49a170bf21b54c9f9b

Tx prefix hash: 172bbf6b782935c0c04e816655827a85526eb10da64697b52f9e7070718d883e
Tx public key: d9159e33a3097a3ef9b7f96476c4800776a306eff8cb676239b5648c5a4ab870
Timestamp: 1729515869 Timestamp [UCT]: 2024-10-21 13:04:29 Age [y:d:h:m:s]: 00:166:23:37:27
Block: 1136411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119142 RingCT/type: yes/0
Extra: 01d9159e33a3097a3ef9b7f96476c4800776a306eff8cb676239b5648c5a4ab870021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc4f902c4fb90a7a89e823c92fcb970bca5b8e4ee562a7f312d029cf23eb07d5 0.600000000000 1619756 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": 1136421, "vin": [ { "gen": { "height": 1136411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc4f902c4fb90a7a89e823c92fcb970bca5b8e4ee562a7f312d029cf23eb07d5" } } ], "extra": [ 1, 217, 21, 158, 51, 163, 9, 122, 62, 249, 183, 249, 100, 118, 196, 128, 7, 118, 163, 6, 239, 248, 203, 103, 98, 57, 181, 100, 140, 90, 74, 184, 112, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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