Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08ea7dd7bce0461d8ea2ec89e400771ef1557f01a16239d8be2f9dc056f3213

Tx prefix hash: 62cc77a986c84adf14da19640100ff7ae55e1fc9376aab566f7fcd1db0db971d
Tx public key: bbc31e198551a2efba54f320ad04a89aa6fb8d754149e264e0ab0e172f8d2d67
Timestamp: 1720802339 Timestamp [UCT]: 2024-07-12 16:38:59 Age [y:d:h:m:s]: 00:245:22:16:24
Block: 1064216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175700 RingCT/type: yes/0
Extra: 01bbc31e198551a2efba54f320ad04a89aa6fb8d754149e264e0ab0e172f8d2d6702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ee9a464eabaaa991bb2ab203f2e7dd49b075a4ba8f7bae98f2a07e61fd776e9 0.600000000000 1534739 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": 1064226, "vin": [ { "gen": { "height": 1064216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ee9a464eabaaa991bb2ab203f2e7dd49b075a4ba8f7bae98f2a07e61fd776e9" } } ], "extra": [ 1, 187, 195, 30, 25, 133, 81, 162, 239, 186, 84, 243, 32, 173, 4, 168, 154, 166, 251, 141, 117, 65, 73, 226, 100, 224, 171, 14, 23, 47, 141, 45, 103, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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