Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b5b2cfda4c4d62de9a533c3d4a6b33af1d14becfffca906dbbcf722bd39779

Tx prefix hash: 9d90c6d79a69c0503be2d5e91a159c13be61065908f782682085b546eb0a9ed3
Tx public key: 94591b6780ba6ae8ff463c3e6a2690d83ef2eb244090de26789c34a8062a6f20
Timestamp: 1700637558 Timestamp [UCT]: 2023-11-22 07:19:18 Age [y:d:h:m:s]: 01:137:06:16:15
Block: 897026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359264 RingCT/type: yes/0
Extra: 0194591b6780ba6ae8ff463c3e6a2690d83ef2eb244090de26789c34a8062a6f20021100000001679a8a81000000000000000000

1 output(s) for total of 0.654305358000 dcy

stealth address amount amount idx
00: e1d140e3dc60e8d015958f235db20b1842c9f2655076e3a9c325327c70d52167 0.654305358000 1353379 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": 897036, "vin": [ { "gen": { "height": 897026 } } ], "vout": [ { "amount": 654305358, "target": { "key": "e1d140e3dc60e8d015958f235db20b1842c9f2655076e3a9c325327c70d52167" } } ], "extra": [ 1, 148, 89, 27, 103, 128, 186, 106, 232, 255, 70, 60, 62, 106, 38, 144, 216, 62, 242, 235, 36, 64, 144, 222, 38, 120, 156, 52, 168, 6, 42, 111, 32, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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