Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b89446e616c37c7c651350b98219601a760d0c17681e6f2a208fe909a29d2c8

Tx prefix hash: a9a424b4feeec10576cb9997dfd4b65d1972b04854f733cfb67348d372012b94
Tx public key: fc509b059f74ed38e6c30825954de3ed5caa4698f7b914b906802d71a6bc4616
Timestamp: 1703982077 Timestamp [UCT]: 2023-12-31 00:21:17 Age [y:d:h:m:s]: 01:325:22:14:22
Block: 924750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491786 RingCT/type: yes/0
Extra: 01fc509b059f74ed38e6c30825954de3ed5caa4698f7b914b906802d71a6bc46160211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1df1da206dd4de22d75de9c2108329694b2bc340e7a1a6c89ba4e0934fa5496 0.600000000000 1382506 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": 924760, "vin": [ { "gen": { "height": 924750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1df1da206dd4de22d75de9c2108329694b2bc340e7a1a6c89ba4e0934fa5496" } } ], "extra": [ 1, 252, 80, 155, 5, 159, 116, 237, 56, 230, 195, 8, 37, 149, 77, 227, 237, 92, 170, 70, 152, 247, 185, 20, 185, 6, 128, 45, 113, 166, 188, 70, 22, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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