Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc0a4e6672d36b04670a69eff08c0726bf0a760ac8bc68299ffeb0c1010cd2c

Tx prefix hash: 6a64fe9258912b6bbcb60392c79af286da27fb0805f9f89c1addff3bf297917b
Tx public key: cf585d0b0bbb3257de8daeb0d681ca3ef8f0da8e003d81aba2c0b7fbb6aa4122
Timestamp: 1676609287 Timestamp [UCT]: 2023-02-17 04:48:07 Age [y:d:h:m:s]: 02:264:13:35:49
Block: 698711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708395 RingCT/type: yes/0
Extra: 01cf585d0b0bbb3257de8daeb0d681ca3ef8f0da8e003d81aba2c0b7fbb6aa412202110000000174b6d784000000000000000000

1 output(s) for total of 2.970847256000 dcy

stealth address amount amount idx
00: 96256ac6ca0a11dd37fd94565e683aba6c149fddf1fc35189e6779002b7b46d1 2.970847256000 1142056 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": 698721, "vin": [ { "gen": { "height": 698711 } } ], "vout": [ { "amount": 2970847256, "target": { "key": "96256ac6ca0a11dd37fd94565e683aba6c149fddf1fc35189e6779002b7b46d1" } } ], "extra": [ 1, 207, 88, 93, 11, 11, 187, 50, 87, 222, 141, 174, 176, 214, 129, 202, 62, 248, 240, 218, 142, 0, 61, 129, 171, 162, 192, 183, 251, 182, 170, 65, 34, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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