Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d5002efa3973321a291e0ed4b6f1e80cfea720163e61d70a75c08eaadc51f7

Tx prefix hash: b0754a61a3edcb63661a853efdf1c83bd91e0fe84e7052a0e0b3d2c1bff8058e
Tx public key: a3e12fba72f62e950dc1e31890ab883cf1e21c8eb914f4527276cfeb5ee34771
Timestamp: 1711771247 Timestamp [UCT]: 2024-03-30 04:00:47 Age [y:d:h:m:s]: 01:221:03:33:03
Block: 989357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416695 RingCT/type: yes/0
Extra: 01a3e12fba72f62e950dc1e31890ab883cf1e21c8eb914f4527276cfeb5ee347710211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc05709e3ac3e3b8f36d945ca62a49c2fb529ee9a2571042c02866ae8337e60 0.600000000000 1449654 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": 989367, "vin": [ { "gen": { "height": 989357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc05709e3ac3e3b8f36d945ca62a49c2fb529ee9a2571042c02866ae8337e60" } } ], "extra": [ 1, 163, 225, 47, 186, 114, 246, 46, 149, 13, 193, 227, 24, 144, 171, 136, 60, 241, 226, 28, 142, 185, 20, 244, 82, 114, 118, 207, 235, 94, 227, 71, 113, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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