Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6fc8e02de073d435a4fddca2eb462b743a74c2888e3d226b4c09b97b91f294

Tx prefix hash: a31ed844cc25bbcf524be5c4ccbd1c11b88e62f29f71977275aa57a1d44fff44
Tx public key: bb8b116090807f03cb346cdf862f06bab4441ba100c8c4de3fadce15a822dab3
Timestamp: 1761932677 Timestamp [UCT]: 2025-10-31 17:44:37 Age [y:d:h:m:s]: 00:006:04:32:02
Block: 1402085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4420 RingCT/type: yes/0
Extra: 01bb8b116090807f03cb346cdf862f06bab4441ba100c8c4de3fadce15a822dab302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7159b40a0f04d7834b3f8c187ead8e3918ffa63c992e8b5a4e91d3371ccc12d0 0.600000000000 1890404 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": 1402095, "vin": [ { "gen": { "height": 1402085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7159b40a0f04d7834b3f8c187ead8e3918ffa63c992e8b5a4e91d3371ccc12d0" } } ], "extra": [ 1, 187, 139, 17, 96, 144, 128, 127, 3, 203, 52, 108, 223, 134, 47, 6, 186, 180, 68, 27, 161, 0, 200, 196, 222, 63, 173, 206, 21, 168, 34, 218, 179, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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