Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a9e82decb29553f60cdd2a3a58c0c9d8e87e3fb4d994073b4840fca9ae060a

Tx prefix hash: 403090579324baf9d231500acacb6050b95f40a8084c645cc5daab3e42f2ec24
Tx public key: 021a712b363627f2c3cbead6f19563bd2457eafebf27c60e03a75687a77d1f55
Timestamp: 1721573377 Timestamp [UCT]: 2024-07-21 14:49:37 Age [y:d:h:m:s]: 00:297:14:40:14
Block: 1070593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212658 RingCT/type: yes/0
Extra: 01021a712b363627f2c3cbead6f19563bd2457eafebf27c60e03a75687a77d1f55021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c29d26e658576e5c322bf7499585c4da5d4543e0dba6531e88a78bd3c5842b39 0.600000000000 1542488 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": 1070603, "vin": [ { "gen": { "height": 1070593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c29d26e658576e5c322bf7499585c4da5d4543e0dba6531e88a78bd3c5842b39" } } ], "extra": [ 1, 2, 26, 113, 43, 54, 54, 39, 242, 195, 203, 234, 214, 241, 149, 99, 189, 36, 87, 234, 254, 191, 39, 198, 14, 3, 167, 86, 135, 167, 125, 31, 85, 2, 17, 0, 0, 0, 1, 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