Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07236dafa7215f2b5f145a866df9998a5cf474123a4212c29db1bb447becb061

Tx prefix hash: 9cee8b92d2129fc177375f24ed145a0dbb8d3589612a6f3f1f5dfb26608d5c1f
Tx public key: 6506c4bfcf7e9004de6036e854572057d6b0e7151b0a2b601c04c2301dc7a037
Timestamp: 1760640205 Timestamp [UCT]: 2025-10-16 18:43:25 Age [y:d:h:m:s]: 00:081:03:32:40
Block: 1391371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58116 RingCT/type: yes/0
Extra: 016506c4bfcf7e9004de6036e854572057d6b0e7151b0a2b601c04c2301dc7a0370211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b92d1edd276917fce134e4c81607bb51baf0dc6e06eac6593ff1811d7a718d9c 0.600000000000 1879618 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": 1391381, "vin": [ { "gen": { "height": 1391371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b92d1edd276917fce134e4c81607bb51baf0dc6e06eac6593ff1811d7a718d9c" } } ], "extra": [ 1, 101, 6, 196, 191, 207, 126, 144, 4, 222, 96, 54, 232, 84, 87, 32, 87, 214, 176, 231, 21, 27, 10, 43, 96, 28, 4, 194, 48, 29, 199, 160, 55, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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