Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a3dd78a742ac10b6ca856e0e1f7a8a9746302c65718a34bb1ab6cd0ae76f3e

Tx prefix hash: 87f316c9e5144b400101a526024d66a660ec7d1dac7de7e6c2bd29d530f68694
Tx public key: e4c80d6c89f31fd2fc2c22baf556ca4aef2707688995140ee81d3fac8e9df12a
Timestamp: 1681078927 Timestamp [UCT]: 2023-04-09 22:22:07 Age [y:d:h:m:s]: 01:277:08:47:28
Block: 735119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459750 RingCT/type: yes/0
Extra: 01e4c80d6c89f31fd2fc2c22baf556ca4aef2707688995140ee81d3fac8e9df12a021100000003faf35c9c000000000000000000

1 output(s) for total of 2.250327956000 dcy

stealth address amount amount idx
00: b8dec0f64ffdbaf20124ddac34e738905152973d29a798911bdf9ed859208a2c 2.250327956000 1181410 of 0

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": 735129, "vin": [ { "gen": { "height": 735119 } } ], "vout": [ { "amount": 2250327956, "target": { "key": "b8dec0f64ffdbaf20124ddac34e738905152973d29a798911bdf9ed859208a2c" } } ], "extra": [ 1, 228, 200, 13, 108, 137, 243, 31, 210, 252, 44, 34, 186, 245, 86, 202, 74, 239, 39, 7, 104, 137, 149, 20, 14, 232, 29, 63, 172, 142, 157, 241, 42, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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