Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c32a36f7243479bcb8ef3a45acfd6c156d03e2e14542c38afe29ebcd458dddcf

Tx prefix hash: d62cd39a248202c52cb16468554627d18e7e06bc4d802f65b865f1ac59a2e5b1
Tx public key: a0f38720e259fa7a64d019498d6f7e4e63cbcdb3ef7adc5b819594c23a60d547
Timestamp: 1724364222 Timestamp [UCT]: 2024-08-22 22:03:42 Age [y:d:h:m:s]: 00:227:10:50:26
Block: 1093751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162403 RingCT/type: yes/0
Extra: 01a0f38720e259fa7a64d019498d6f7e4e63cbcdb3ef7adc5b819594c23a60d54702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166cf429281340b53efec7a63f57b076ce69a942d346e786e0002956c0c691bd 0.600000000000 1568758 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": 1093761, "vin": [ { "gen": { "height": 1093751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166cf429281340b53efec7a63f57b076ce69a942d346e786e0002956c0c691bd" } } ], "extra": [ 1, 160, 243, 135, 32, 226, 89, 250, 122, 100, 208, 25, 73, 141, 111, 126, 78, 99, 203, 205, 179, 239, 122, 220, 91, 129, 149, 148, 194, 58, 96, 213, 71, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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