Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eeff775c9ef761c17d583d9e72fa083cd56a2853944fb183971f249f7293ea5

Tx prefix hash: 0b7dabeb8be35e0657bbb8ed0d8dce9b637eb17cfe116059d013b2370b7a16c0
Tx public key: 88c6c910f492073f4b8aa43ff2a79bd5a0bb519c7dc73aaa57c6a2f328feb241
Timestamp: 1709142581 Timestamp [UCT]: 2024-02-28 17:49:41 Age [y:d:h:m:s]: 01:085:03:42:07
Block: 967551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321906 RingCT/type: yes/0
Extra: 0188c6c910f492073f4b8aa43ff2a79bd5a0bb519c7dc73aaa57c6a2f328feb24102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25bdcbe78ef2d529ccdc22fd0cf73f928510ee51f542c57b875bbb8e69288d74 0.600000000000 1427334 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": 967561, "vin": [ { "gen": { "height": 967551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25bdcbe78ef2d529ccdc22fd0cf73f928510ee51f542c57b875bbb8e69288d74" } } ], "extra": [ 1, 136, 198, 201, 16, 244, 146, 7, 63, 75, 138, 164, 63, 242, 167, 155, 213, 160, 187, 81, 156, 125, 199, 58, 170, 87, 198, 162, 243, 40, 254, 178, 65, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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