Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 980f3c9f69e28cb2d97879293e7cf7cd25ad7f759bff15f34b50e265c74ee241

Tx prefix hash: c73194d1e5c7378ce3ed975a19e8a29fe89c0bdd202da30390bf8e3ab772ccab
Tx public key: f4c8893c0c4e28f04b638d2c00425e6ea511ae0db7423efe0227b14a8e55c24b
Timestamp: 1699880259 Timestamp [UCT]: 2023-11-13 12:57:39 Age [y:d:h:m:s]: 01:181:15:10:47
Block: 890757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391013 RingCT/type: yes/0
Extra: 01f4c8893c0c4e28f04b638d2c00425e6ea511ae0db7423efe0227b14a8e55c24b021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.686360505000 dcy

stealth address amount amount idx
00: 69ca89fb63231cd54f13be1c6ce0dbd329e0ae63c99ce73576409da3710d0500 0.686360505000 1346788 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": 890767, "vin": [ { "gen": { "height": 890757 } } ], "vout": [ { "amount": 686360505, "target": { "key": "69ca89fb63231cd54f13be1c6ce0dbd329e0ae63c99ce73576409da3710d0500" } } ], "extra": [ 1, 244, 200, 137, 60, 12, 78, 40, 240, 75, 99, 141, 44, 0, 66, 94, 110, 165, 17, 174, 13, 183, 66, 62, 254, 2, 39, 177, 74, 142, 85, 194, 75, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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