Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39723c02fa733a25cf7150e3bc256fd57011a7267750189f1672ebb28a52610e

Tx prefix hash: 9f611b7a29c9744792db048a007c673e30464fcaafce6c03b3be4c86c014a1ef
Tx public key: b4fa9c543603487ffcb25a7f9b157f9921bd7a50f52a57b2c1fa8892666fcb7b
Timestamp: 1709816888 Timestamp [UCT]: 2024-03-07 13:08:08 Age [y:d:h:m:s]: 01:102:09:44:29
Block: 973145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334099 RingCT/type: yes/0
Extra: 01b4fa9c543603487ffcb25a7f9b157f9921bd7a50f52a57b2c1fa8892666fcb7b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5b866b4e2515c1e7ecc98ce6291a3f08699c115a311e2b490d19ab3bd7570d 0.600000000000 1433078 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": 973155, "vin": [ { "gen": { "height": 973145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5b866b4e2515c1e7ecc98ce6291a3f08699c115a311e2b490d19ab3bd7570d" } } ], "extra": [ 1, 180, 250, 156, 84, 54, 3, 72, 127, 252, 178, 90, 127, 155, 21, 127, 153, 33, 189, 122, 80, 245, 42, 87, 178, 193, 250, 136, 146, 102, 111, 203, 123, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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