Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74dc71209c11dde8fdfd2ba67bd2105030735177b34c4c3deff923db76968af0

Tx prefix hash: 00306147f95b04f9dce8e6927c5ea773f2d876102cde043262f80d7061e13970
Tx public key: c250039efb02f510ce334ad1fd4f9adac80ea00ebaf2958fe136f3fdf4ff7054
Timestamp: 1735857090 Timestamp [UCT]: 2025-01-02 22:31:30 Age [y:d:h:m:s]: 00:121:07:55:09
Block: 1188886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86514 RingCT/type: yes/0
Extra: 01c250039efb02f510ce334ad1fd4f9adac80ea00ebaf2958fe136f3fdf4ff70540211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1f1afc457ecd185d960959d6c0be5de926db92b9ad52b5fdc97043e0b52499 0.600000000000 1675391 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": 1188896, "vin": [ { "gen": { "height": 1188886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1f1afc457ecd185d960959d6c0be5de926db92b9ad52b5fdc97043e0b52499" } } ], "extra": [ 1, 194, 80, 3, 158, 251, 2, 245, 16, 206, 51, 74, 209, 253, 79, 154, 218, 200, 14, 160, 14, 186, 242, 149, 143, 225, 54, 243, 253, 244, 255, 112, 84, 2, 17, 0, 0, 0, 1, 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