Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 204d03f391e2aa6e2ebe9b8d80e4dae45b78e1fce006f2f9664e1b9b24dec3b0

Tx prefix hash: db3dff7b9e5d3857e0b83286c43c089073f7be1ca446fcdd08f463b59198175e
Tx public key: 6e5adc88b22c5b8bfc049975abf828464b95c2228f10044d36e5e288a7a317fa
Timestamp: 1716139031 Timestamp [UCT]: 2024-05-19 17:17:11 Age [y:d:h:m:s]: 00:338:06:46:36
Block: 1025545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241790 RingCT/type: yes/0
Extra: 016e5adc88b22c5b8bfc049975abf828464b95c2228f10044d36e5e288a7a317fa02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5d407288619746737b122242936118ee8fca6bd6c8abf682db3034ff7e70c1e 0.600000000000 1492130 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": 1025555, "vin": [ { "gen": { "height": 1025545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5d407288619746737b122242936118ee8fca6bd6c8abf682db3034ff7e70c1e" } } ], "extra": [ 1, 110, 90, 220, 136, 178, 44, 91, 139, 252, 4, 153, 117, 171, 248, 40, 70, 75, 149, 194, 34, 143, 16, 4, 77, 54, 229, 226, 136, 167, 163, 23, 250, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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