Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1e54c0c25db6215ce6b3cb37cc4457c9a81d9ee3c2deb4423e0a17cc4a69a9

Tx prefix hash: ed884b48f194d59364469c8195dfae5b4e4eed97ad37002796db84760608f5c9
Tx public key: f3323968defd25aba409bcbb94d5a6528b9f3d2eb90ec059d04d12e90f532e40
Timestamp: 1716846741 Timestamp [UCT]: 2024-05-27 21:52:21 Age [y:d:h:m:s]: 00:337:07:27:47
Block: 1031428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241084 RingCT/type: yes/0
Extra: 01f3323968defd25aba409bcbb94d5a6528b9f3d2eb90ec059d04d12e90f532e400211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38ee69a4d20ca8d43190fcfb65a29bf431cd8f53042e667de2f8223514fcd8a 0.600000000000 1499869 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": 1031438, "vin": [ { "gen": { "height": 1031428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38ee69a4d20ca8d43190fcfb65a29bf431cd8f53042e667de2f8223514fcd8a" } } ], "extra": [ 1, 243, 50, 57, 104, 222, 253, 37, 171, 164, 9, 188, 187, 148, 213, 166, 82, 139, 159, 61, 46, 185, 14, 192, 89, 208, 77, 18, 233, 15, 83, 46, 64, 2, 17, 0, 0, 0, 2, 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