Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea64add09504d0f2740d1152c956b716614494c452e2121684b3b44658b0d162

Tx prefix hash: 6cdcca4250e58ec4ab2c7b9e01f7500967338118f86e2d5b52f2f4495b7d0f07
Tx public key: 87f1c65653e9c02b6a4a5f1aee4cf6f4e246aca743dedf72469824b25649eb75
Timestamp: 1704113498 Timestamp [UCT]: 2024-01-01 12:51:38 Age [y:d:h:m:s]: 00:328:06:36:21
Block: 925840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235058 RingCT/type: yes/0
Extra: 0187f1c65653e9c02b6a4a5f1aee4cf6f4e246aca743dedf72469824b25649eb75021100000005ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77388918907cc85e1d3a2f42bab887294430adb53ca11d08381f021c2c895d9a 0.600000000000 1383610 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": 925850, "vin": [ { "gen": { "height": 925840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77388918907cc85e1d3a2f42bab887294430adb53ca11d08381f021c2c895d9a" } } ], "extra": [ 1, 135, 241, 198, 86, 83, 233, 192, 43, 106, 74, 95, 26, 238, 76, 246, 244, 226, 70, 172, 167, 67, 222, 223, 114, 70, 152, 36, 178, 86, 73, 235, 117, 2, 17, 0, 0, 0, 5, 172, 50, 141, 17, 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