Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b394e00399f0a6b2002b5038462071726fbb590210d4c6b0ebf3073924cf59c4

Tx prefix hash: 326c26a8f184d86d9dc007582320886afc596204577bcfe6d3f309bb33ec345c
Tx public key: 73762126f99ea4a39a6f6d4c7a973aa9d41813b4ba9191be289958b55e2f28b8
Timestamp: 1735711767 Timestamp [UCT]: 2025-01-01 06:09:27 Age [y:d:h:m:s]: 00:099:00:37:42
Block: 1187678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70572 RingCT/type: yes/0
Extra: 0173762126f99ea4a39a6f6d4c7a973aa9d41813b4ba9191be289958b55e2f28b8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 736d7e51dc28e295de88301b3f23540b69f2f60add8046b02446f4e14e8b6455 0.600000000000 1674171 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": 1187688, "vin": [ { "gen": { "height": 1187678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "736d7e51dc28e295de88301b3f23540b69f2f60add8046b02446f4e14e8b6455" } } ], "extra": [ 1, 115, 118, 33, 38, 249, 158, 164, 163, 154, 111, 109, 76, 122, 151, 58, 169, 212, 24, 19, 180, 186, 145, 145, 190, 40, 153, 88, 181, 94, 47, 40, 184, 2, 17, 0, 0, 0, 3, 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