Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16fc964c21084aab973b14c58d54093c6959028d3f975e14236b194ce3f57bf5

Tx prefix hash: f20fd66623dfd88f463d9c9e4afdee12de17e726ccab8b8d581fea8f2e8260e7
Tx public key: a113fb9bc216d479473500822cf365ff0d6724ebe3b9eb0388d6231ea1eb2f97
Timestamp: 1578830248 Timestamp [UCT]: 2020-01-12 11:57:28 Age [y:d:h:m:s]: 05:135:11:40:50
Block: 43918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247036 RingCT/type: yes/0
Extra: 01a113fb9bc216d479473500822cf365ff0d6724ebe3b9eb0388d6231ea1eb2f970211000000074943cd9f000000000000000000

1 output(s) for total of 439.017949177000 dcy

stealth address amount amount idx
00: 1e4d3cf4a5c404c695ff2b1fca3075ece264a6511ae6d05461d8bb8dcd1009b6 439.017949177000 79724 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": 43928, "vin": [ { "gen": { "height": 43918 } } ], "vout": [ { "amount": 439017949177, "target": { "key": "1e4d3cf4a5c404c695ff2b1fca3075ece264a6511ae6d05461d8bb8dcd1009b6" } } ], "extra": [ 1, 161, 19, 251, 155, 194, 22, 212, 121, 71, 53, 0, 130, 44, 243, 101, 255, 13, 103, 36, 235, 227, 185, 235, 3, 136, 214, 35, 30, 161, 235, 47, 151, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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