Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3902b59f4978b85e40cc3fe4797fd8d96d8016a3bea0e3d5bc4f647d3cfea70

Tx prefix hash: 79d3e8cd925f485cb658c864e465742bbb4d9c5e987c9f1979411f022dc07e8b
Tx public key: 763b29a9182b1b2f877e1362090d5dfe6ec63256afba0a8be4694a9cd6a56c79
Timestamp: 1698516171 Timestamp [UCT]: 2023-10-28 18:02:51 Age [y:d:h:m:s]: 01:140:18:07:26
Block: 879658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361606 RingCT/type: yes/0
Extra: 01763b29a9182b1b2f877e1362090d5dfe6ec63256afba0a8be4694a9cd6a56c7902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.747012546000 dcy

stealth address amount amount idx
00: cc8804acd0ac6d1b420774b1c10e48ab950c09df391796c8ff6fdb0527edfd90 0.747012546000 1335192 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": 879668, "vin": [ { "gen": { "height": 879658 } } ], "vout": [ { "amount": 747012546, "target": { "key": "cc8804acd0ac6d1b420774b1c10e48ab950c09df391796c8ff6fdb0527edfd90" } } ], "extra": [ 1, 118, 59, 41, 169, 24, 43, 27, 47, 135, 126, 19, 98, 9, 13, 93, 254, 110, 198, 50, 86, 175, 186, 10, 139, 228, 105, 74, 156, 214, 165, 108, 121, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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