Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf958f24d6441c6371bda37d4772b8c19f0a106165e52eed0f835bf53bf7839d

Tx prefix hash: c6477e6ea232d2a0ecf7db32dc169e7a22a95b55b286b92d2e426f2a7f67798f
Tx public key: d97f335fbce9b293c7f53a516de0043ac03702987304607484df2569b6cb844f
Timestamp: 1717492397 Timestamp [UCT]: 2024-06-04 09:13:17 Age [y:d:h:m:s]: 01:018:22:36:16
Block: 1036777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274227 RingCT/type: yes/0
Extra: 01d97f335fbce9b293c7f53a516de0043ac03702987304607484df2569b6cb844f0211000000034385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61dcb5d907f05868ce124e9e3f496a77e19729275def2a3c85dc6d2bc082db7c 0.600000000000 1505306 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": 1036787, "vin": [ { "gen": { "height": 1036777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61dcb5d907f05868ce124e9e3f496a77e19729275def2a3c85dc6d2bc082db7c" } } ], "extra": [ 1, 217, 127, 51, 95, 188, 233, 178, 147, 199, 245, 58, 81, 109, 224, 4, 58, 192, 55, 2, 152, 115, 4, 96, 116, 132, 223, 37, 105, 182, 203, 132, 79, 2, 17, 0, 0, 0, 3, 67, 133, 54, 42, 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