Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de3dc95d1f74f585b65998d0a4bac49f405aabb2652a03d8937ce399d9107d1

Tx prefix hash: e534252b36fbd38d68d614cc537fff362366ee06975bbfd4d9c6fa05d8ffd042
Tx public key: 1e99f12188d6defdf706d9610af17ce80e28e86f1b23a4931935806946d47cf5
Timestamp: 1723242440 Timestamp [UCT]: 2024-08-09 22:27:20 Age [y:d:h:m:s]: 00:307:11:13:02
Block: 1084434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219621 RingCT/type: yes/0
Extra: 011e99f12188d6defdf706d9610af17ce80e28e86f1b23a4931935806946d47cf5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf2716bd7e441b92a3d1e66d2a46b9468a063485a61ab4875bdec40ab9eecc3 0.600000000000 1558711 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": 1084444, "vin": [ { "gen": { "height": 1084434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf2716bd7e441b92a3d1e66d2a46b9468a063485a61ab4875bdec40ab9eecc3" } } ], "extra": [ 1, 30, 153, 241, 33, 136, 214, 222, 253, 247, 6, 217, 97, 10, 241, 124, 232, 14, 40, 232, 111, 27, 35, 164, 147, 25, 53, 128, 105, 70, 212, 124, 245, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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