Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c01a9f08f3e5e1c30dc26c993f3e5f4248f2a847c17fd4a16bfcf06abd8b0f

Tx prefix hash: 6ab1b1dcbba3ffad5a6c5547013aa1abf3b5e2400a78bb313c859a1e3d4ecfc0
Tx public key: 1730c8f47bbbeb06126162069e2e58eae3810278853dfa7926bbce2c67d36b16
Timestamp: 1712525824 Timestamp [UCT]: 2024-04-07 21:37:04 Age [y:d:h:m:s]: 01:045:11:41:15
Block: 995559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293535 RingCT/type: yes/0
Extra: 011730c8f47bbbeb06126162069e2e58eae3810278853dfa7926bbce2c67d36b160211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 436f77f5090469f7dc6869ae6e116413b0cbaf1be8f6fe67ad842530124a1d87 0.600000000000 1455969 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": 995569, "vin": [ { "gen": { "height": 995559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "436f77f5090469f7dc6869ae6e116413b0cbaf1be8f6fe67ad842530124a1d87" } } ], "extra": [ 1, 23, 48, 200, 244, 123, 187, 235, 6, 18, 97, 98, 6, 158, 46, 88, 234, 227, 129, 2, 120, 133, 61, 250, 121, 38, 187, 206, 44, 103, 211, 107, 22, 2, 17, 0, 0, 0, 1, 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