Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0de5d8d00cf57a684800a0d19b6271437bb964c8fe5c7bd740421a30e0b769f

Tx prefix hash: 5ea30fcb6470e054b49b60a0132ebaa140f282cfd8a24478206c5760919acd5e
Tx public key: f9a4eca6bba2e6a6b1dfb203d3250d1047d3fc48bf28fe1232a9f139f736ad97
Timestamp: 1721726559 Timestamp [UCT]: 2024-07-23 09:22:39 Age [y:d:h:m:s]: 00:265:14:27:25
Block: 1071860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189750 RingCT/type: yes/0
Extra: 01f9a4eca6bba2e6a6b1dfb203d3250d1047d3fc48bf28fe1232a9f139f736ad97021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a16d4f97bdd3577bb3ec766e152c11cf0d4c98c8c4bf0977eea8606456a5d6cd 0.600000000000 1544245 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": 1071870, "vin": [ { "gen": { "height": 1071860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a16d4f97bdd3577bb3ec766e152c11cf0d4c98c8c4bf0977eea8606456a5d6cd" } } ], "extra": [ 1, 249, 164, 236, 166, 187, 162, 230, 166, 177, 223, 178, 3, 211, 37, 13, 16, 71, 211, 252, 72, 191, 40, 254, 18, 50, 169, 241, 57, 247, 54, 173, 151, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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