Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b91be01d0395ac752246d6a47370d614c641cf5c31060cfe13f8e7f1d2d34be

Tx prefix hash: 6f780d8f4b9320432eca98d5c8679b66445f5e05d0deab295d4493d70f61df01
Tx public key: 859f1516d7faa1dd2d31615ab548c6011a5a49f349bcfd6a8cdb0678261f6c66
Timestamp: 1735516476 Timestamp [UCT]: 2024-12-29 23:54:36 Age [y:d:h:m:s]: 00:305:16:37:09
Block: 1186057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215994 RingCT/type: yes/0
Extra: 01859f1516d7faa1dd2d31615ab548c6011a5a49f349bcfd6a8cdb0678261f6c660211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 175e4bb2308fd6f310762512aad5f815544a977c4f9b0b9ecd7790e10eb13766 0.600000000000 1672532 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": 1186067, "vin": [ { "gen": { "height": 1186057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "175e4bb2308fd6f310762512aad5f815544a977c4f9b0b9ecd7790e10eb13766" } } ], "extra": [ 1, 133, 159, 21, 22, 215, 250, 161, 221, 45, 49, 97, 90, 181, 72, 198, 1, 26, 90, 73, 243, 73, 188, 253, 106, 140, 219, 6, 120, 38, 31, 108, 102, 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