Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d6c2874116e55b009d69c39aa0700dac9d78c80cc5753d5877f7a3bb5a6d8e

Tx prefix hash: 329b2b73ff1eed98420fbf4ae86f3d241c24f9c1a13bdf8dfd371ea31a253978
Tx public key: 12a2f8105d6dcfb5c2e9424b1cddd7c7f8ef5b2a113257ac0fcf66c617892987
Timestamp: 1709696916 Timestamp [UCT]: 2024-03-06 03:48:36 Age [y:d:h:m:s]: 01:103:23:32:12
Block: 972143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335238 RingCT/type: yes/0
Extra: 0112a2f8105d6dcfb5c2e9424b1cddd7c7f8ef5b2a113257ac0fcf66c6178929870211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24436e10dc6d23fa3e4068a8bc2b34c57e45fb3ebb72ffef7a4cccbd43d4fe23 0.600000000000 1432048 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": 972153, "vin": [ { "gen": { "height": 972143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24436e10dc6d23fa3e4068a8bc2b34c57e45fb3ebb72ffef7a4cccbd43d4fe23" } } ], "extra": [ 1, 18, 162, 248, 16, 93, 109, 207, 181, 194, 233, 66, 75, 28, 221, 215, 199, 248, 239, 91, 42, 17, 50, 87, 172, 15, 207, 102, 198, 23, 137, 41, 135, 2, 17, 0, 0, 0, 9, 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