Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff3da3968e192e9e351573da3c16adce0ff7fad41209b1091e0b30de26cb10b

Tx prefix hash: bb88b86a62fc8a0b98f8d073ac90f7570b7cc8c26c1b74aed97369e0aa997c41
Tx public key: 179dfd300a7a860f28bfa20d96790db7a56afdfb75ab85743aa241d40981566d
Timestamp: 1719570446 Timestamp [UCT]: 2024-06-28 10:27:26 Age [y:d:h:m:s]: 00:293:19:19:27
Block: 1053997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209940 RingCT/type: yes/0
Extra: 01179dfd300a7a860f28bfa20d96790db7a56afdfb75ab85743aa241d40981566d0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e668feff3f4a9abd18d2a52f0878d5853232e48a413d3ba485b5ce76aef648 0.600000000000 1524356 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": 1054007, "vin": [ { "gen": { "height": 1053997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e668feff3f4a9abd18d2a52f0878d5853232e48a413d3ba485b5ce76aef648" } } ], "extra": [ 1, 23, 157, 253, 48, 10, 122, 134, 15, 40, 191, 162, 13, 150, 121, 13, 183, 165, 106, 253, 251, 117, 171, 133, 116, 58, 162, 65, 212, 9, 129, 86, 109, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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