Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0759d04148cb98f999f188e96bb67319525f3ca8b261695e0b1761fb6b3b65b

Tx prefix hash: 181765e11b45ab58d3d0b4a0b402197d082e1fa8d902adef9861631d1dc66dc8
Tx public key: 7a1600c3e92d1747c288802c4585984159cc7ba73a11ec927cb7e42016363994
Timestamp: 1623966730 Timestamp [UCT]: 2021-06-17 21:52:10 Age [y:d:h:m:s]: 04:138:13:04:16
Block: 279462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123849 RingCT/type: yes/0
Extra: 017a1600c3e92d1747c288802c4585984159cc7ba73a11ec927cb7e4201636399402110000003897247f25000000000000000000

1 output(s) for total of 72.782489094000 dcy

stealth address amount amount idx
00: 93f6801488fb262a7c486b184dfbc3b88f2ea2bf36a02e50105f75ff6c96e4b1 72.782489094000 585301 of 0

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": 279472, "vin": [ { "gen": { "height": 279462 } } ], "vout": [ { "amount": 72782489094, "target": { "key": "93f6801488fb262a7c486b184dfbc3b88f2ea2bf36a02e50105f75ff6c96e4b1" } } ], "extra": [ 1, 122, 22, 0, 195, 233, 45, 23, 71, 194, 136, 128, 44, 69, 133, 152, 65, 89, 204, 123, 167, 58, 17, 236, 146, 124, 183, 228, 32, 22, 54, 57, 148, 2, 17, 0, 0, 0, 56, 151, 36, 127, 37, 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