Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01baf82d07d768192322b7a3f59c73730b6804168c2033570ca9645191b5ddd

Tx prefix hash: dd984655d864ce4e81b3bdb16473b21ff9bf1c0d5f0591600ef73f452cac403e
Tx public key: fbe10356d27ab2a2043bde6abb4f6ae0bbb93e5a395fe8d4c9c1ac2171faaea7
Timestamp: 1758819800 Timestamp [UCT]: 2025-09-25 17:03:20 Age [y:d:h:m:s]: 00:043:14:54:20
Block: 1376291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31225 RingCT/type: yes/0
Extra: 01fbe10356d27ab2a2043bde6abb4f6ae0bbb93e5a395fe8d4c9c1ac2171faaea702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeaa18d13607542e9c8b6772b079c0a7ee686c27ea18536ecf18a04aea2638fe 0.600000000000 1864382 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": 1376301, "vin": [ { "gen": { "height": 1376291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeaa18d13607542e9c8b6772b079c0a7ee686c27ea18536ecf18a04aea2638fe" } } ], "extra": [ 1, 251, 225, 3, 86, 210, 122, 178, 162, 4, 59, 222, 106, 187, 79, 106, 224, 187, 185, 62, 90, 57, 95, 232, 212, 201, 193, 172, 33, 113, 250, 174, 167, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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