Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3130dd9fbba4e3077e54212037c3718c8cbef3a2cf03568117b71c3ea5db943a

Tx prefix hash: 1890341cc9882d6374f7919e1c02466b253f6750a4f3426f2465965bdf1719c5
Tx public key: d3ff07e8a9ffdad2363f79d2efd7a9eb37b1f38eff7d023763f7bb06b47f4511
Timestamp: 1732821862 Timestamp [UCT]: 2024-11-28 19:24:22 Age [y:d:h:m:s]: 00:116:04:33:44
Block: 1163758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82831 RingCT/type: yes/0
Extra: 01d3ff07e8a9ffdad2363f79d2efd7a9eb37b1f38eff7d023763f7bb06b47f45110211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851b3b59c374f27e95995d4ac176ebeb5b7de579d7c1cdd6448d8c4fd4207176 0.600000000000 1649427 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": 1163768, "vin": [ { "gen": { "height": 1163758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851b3b59c374f27e95995d4ac176ebeb5b7de579d7c1cdd6448d8c4fd4207176" } } ], "extra": [ 1, 211, 255, 7, 232, 169, 255, 218, 210, 54, 63, 121, 210, 239, 215, 169, 235, 55, 177, 243, 142, 255, 125, 2, 55, 99, 247, 187, 6, 180, 127, 69, 17, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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