Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 154755251658f2d8c82df1a9d9dfef65ecae21a988999e0e6348367e9b8bdf8d

Tx prefix hash: 022a83c104d90dda61860fe70c99be93d586aa93c80472820910125ba9b8b69a
Tx public key: 81913f9b237b8ae67385f540387634092e501b420b8502e5b0045c4e610221fd
Timestamp: 1759830294 Timestamp [UCT]: 2025-10-07 09:44:54 Age [y:d:h:m:s]: 00:033:14:41:41
Block: 1384646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24074 RingCT/type: yes/0
Extra: 0181913f9b237b8ae67385f540387634092e501b420b8502e5b0045c4e610221fd02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d01a4ba9e9ca930f1a454c0bfb5c218517e0260f3384809d9285da021a8dcc94 0.600000000000 1872799 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": 1384656, "vin": [ { "gen": { "height": 1384646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d01a4ba9e9ca930f1a454c0bfb5c218517e0260f3384809d9285da021a8dcc94" } } ], "extra": [ 1, 129, 145, 63, 155, 35, 123, 138, 230, 115, 133, 245, 64, 56, 118, 52, 9, 46, 80, 27, 66, 11, 133, 2, 229, 176, 4, 92, 78, 97, 2, 33, 253, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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