Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 447f169f167b0d8685f0589914e25fdb8e7420fa8b82f2d7d410b766baf3ae22

Tx prefix hash: f808beeb00678a56c94a927881d6b372ebb22dc2c9f28229457c877bf39df08b
Tx public key: 8867bb84ee8bf9a8f5ee8bc52af161bd54d9e80bea8d2f0ee19900c29d9f64ce
Timestamp: 1705036253 Timestamp [UCT]: 2024-01-12 05:10:53 Age [y:d:h:m:s]: 01:154:00:02:22
Block: 933470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371148 RingCT/type: yes/0
Extra: 018867bb84ee8bf9a8f5ee8bc52af161bd54d9e80bea8d2f0ee19900c29d9f64ce02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d990b8aecbf0dcdb271e131c0ef0f06400f579b39c64ea4dda94459430231d0 0.600000000000 1391432 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": 933480, "vin": [ { "gen": { "height": 933470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d990b8aecbf0dcdb271e131c0ef0f06400f579b39c64ea4dda94459430231d0" } } ], "extra": [ 1, 136, 103, 187, 132, 238, 139, 249, 168, 245, 238, 139, 197, 42, 241, 97, 189, 84, 217, 232, 11, 234, 141, 47, 14, 225, 153, 0, 194, 157, 159, 100, 206, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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