Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffc27db3061e0d99fb58675824a5fb050951e30b38b75a7a9c39a895021447ac

Tx prefix hash: 49319944b4ae3fa6e8bac91a7a662dbf22c78a2ec85238548290ac06d14a1dfe
Tx public key: 6d1e618d9b9fc86a35a19c8e73f73f49969788c165e7da14bbd9bc8badba44b2
Timestamp: 1734770019 Timestamp [UCT]: 2024-12-21 08:33:39 Age [y:d:h:m:s]: 00:101:02:04:23
Block: 1179912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72001 RingCT/type: yes/0
Extra: 016d1e618d9b9fc86a35a19c8e73f73f49969788c165e7da14bbd9bc8badba44b2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f028a0aaa4529b31e92bdbbddfd6227e0f8c83218dab7292a6fce0800c23f373 0.600000000000 1666313 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": 1179922, "vin": [ { "gen": { "height": 1179912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f028a0aaa4529b31e92bdbbddfd6227e0f8c83218dab7292a6fce0800c23f373" } } ], "extra": [ 1, 109, 30, 97, 141, 155, 159, 200, 106, 53, 161, 156, 142, 115, 247, 63, 73, 150, 151, 136, 193, 101, 231, 218, 20, 187, 217, 188, 139, 173, 186, 68, 178, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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