Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed37c4c640658f41fd10ebcc300f5e18009c36bb4aceb41f66a3044e9bdf5ea1

Tx prefix hash: 2806fee35ac3e2644787557b8e2aa207b0405652517748a858d01298bf51247a
Tx public key: ed04fd4162fbf231d2af6f8a208e89ff08e7d3b89573a93f8dfec38c4ecd10b5
Timestamp: 1703456914 Timestamp [UCT]: 2023-12-24 22:28:34 Age [y:d:h:m:s]: 01:172:12:16:44
Block: 920412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384377 RingCT/type: yes/0
Extra: 01ed04fd4162fbf231d2af6f8a208e89ff08e7d3b89573a93f8dfec38c4ecd10b5021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bc8e9a0a04f4161ecc42634fef08def587fd71c3c2eb1b6fa78e1cdad58f0e9 0.600000000000 1378090 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": 920422, "vin": [ { "gen": { "height": 920412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bc8e9a0a04f4161ecc42634fef08def587fd71c3c2eb1b6fa78e1cdad58f0e9" } } ], "extra": [ 1, 237, 4, 253, 65, 98, 251, 242, 49, 210, 175, 111, 138, 32, 142, 137, 255, 8, 231, 211, 184, 149, 115, 169, 63, 141, 254, 195, 140, 78, 205, 16, 181, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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