Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b937f6e98158c215592d4f7ead177e82b4e9a16b134de225dc88d4b5243a93

Tx prefix hash: d935ef8dc2c89dcc260f7e6427a92607e7007f2b0103a707bd9cd1b5795cd14e
Tx public key: 556ee6e5d1ef25e5fff5842e73362129edf1c6669ee20d15fdbce726d1588c83
Timestamp: 1736237714 Timestamp [UCT]: 2025-01-07 08:15:14 Age [y:d:h:m:s]: 00:073:15:13:07
Block: 1192046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52392 RingCT/type: yes/0
Extra: 01556ee6e5d1ef25e5fff5842e73362129edf1c6669ee20d15fdbce726d1588c83021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9af7d04afb50e286cadc2fbfb4df144d8adca28848dfebfab5975b8626c10c8a 0.600000000000 1678591 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": 1192056, "vin": [ { "gen": { "height": 1192046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9af7d04afb50e286cadc2fbfb4df144d8adca28848dfebfab5975b8626c10c8a" } } ], "extra": [ 1, 85, 110, 230, 229, 209, 239, 37, 229, 255, 245, 132, 46, 115, 54, 33, 41, 237, 241, 198, 102, 158, 226, 13, 21, 253, 188, 231, 38, 209, 88, 140, 131, 2, 17, 0, 0, 0, 7, 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