Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc51119f05fc8d8801e47866e586c8875f110f8c6c175658d5d4ae27981e58de

Tx prefix hash: bf681bceee781cfefcc668d292d7d139020ec714b511f65b0dddac6e9b6eed13
Tx public key: e497a770f7c3134e3889e4222a123df7b15e364caccb90ea00b6a0bff1365a73
Timestamp: 1715659927 Timestamp [UCT]: 2024-05-14 04:12:07 Age [y:d:h:m:s]: 00:321:21:02:34
Block: 1021577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230062 RingCT/type: yes/0
Extra: 01e497a770f7c3134e3889e4222a123df7b15e364caccb90ea00b6a0bff1365a730211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fe223eece44741acb74a8e3f5d41128774cbfd931e9cba9aab41a431594e521 0.600000000000 1485936 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": 1021587, "vin": [ { "gen": { "height": 1021577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fe223eece44741acb74a8e3f5d41128774cbfd931e9cba9aab41a431594e521" } } ], "extra": [ 1, 228, 151, 167, 112, 247, 195, 19, 78, 56, 137, 228, 34, 42, 18, 61, 247, 177, 94, 54, 76, 172, 203, 144, 234, 0, 182, 160, 191, 241, 54, 90, 115, 2, 17, 0, 0, 0, 5, 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