Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe477f0b37ec04e6dd8fa191596b4f6470186e62de43de9f1b4bf18387c57a6e

Tx prefix hash: de588a7809a6b62be44d48095a48e2fbf212ea7ff4f90965ad1aa9245d2ecd2c
Tx public key: 2071bd022f2f61a3ca2bf4b2ff86c696e1a5a8bbcce7e5e5d7117503c365c910
Timestamp: 1736825521 Timestamp [UCT]: 2025-01-14 03:32:01 Age [y:d:h:m:s]: 00:156:07:01:58
Block: 1196899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111394 RingCT/type: yes/0
Extra: 012071bd022f2f61a3ca2bf4b2ff86c696e1a5a8bbcce7e5e5d7117503c365c9100211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abfe3b321550cf57ee51474866b24d659b22923a7cffcb7fec4e4a5e86ced4d7 0.600000000000 1683504 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": 1196909, "vin": [ { "gen": { "height": 1196899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abfe3b321550cf57ee51474866b24d659b22923a7cffcb7fec4e4a5e86ced4d7" } } ], "extra": [ 1, 32, 113, 189, 2, 47, 47, 97, 163, 202, 43, 244, 178, 255, 134, 198, 150, 225, 165, 168, 187, 204, 231, 229, 229, 215, 17, 117, 3, 195, 101, 201, 16, 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