Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a26fc916fc302d8767c9894549f753b222c5e41575008c21f4820a9d84ace6f

Tx prefix hash: a6e9ae77bc0cd7583608b7439e6afc116c27550e92c115daf04997281104e359
Tx public key: 8d67ce51c2a5f0827e03d41b395df892cf6651b9d02d775a373d8f412491781b
Timestamp: 1730560609 Timestamp [UCT]: 2024-11-02 15:16:49 Age [y:d:h:m:s]: 00:150:16:01:18
Block: 1145016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107514 RingCT/type: yes/0
Extra: 018d67ce51c2a5f0827e03d41b395df892cf6651b9d02d775a373d8f412491781b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1f1fdd707841d12616a06737e358583f2036a2811f8bf6e2c28715314ae795b 0.600000000000 1629377 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": 1145026, "vin": [ { "gen": { "height": 1145016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1f1fdd707841d12616a06737e358583f2036a2811f8bf6e2c28715314ae795b" } } ], "extra": [ 1, 141, 103, 206, 81, 194, 165, 240, 130, 126, 3, 212, 27, 57, 93, 248, 146, 207, 102, 81, 185, 208, 45, 119, 90, 55, 61, 143, 65, 36, 145, 120, 27, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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