Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a2f38e364fe157fae9d677c8cd6af7f7a156450a154e75b9ccc7e128615c4fd

Tx prefix hash: 96e76bc200efb67b8586a436482ceef0d1b6ea0321ea46c4acc1a7f4e659f83f
Tx public key: 7fdb520fc36873b1e8f651ed91f7ccccb6cb6818d3d1501ee10fc73e20c33c22
Timestamp: 1713127854 Timestamp [UCT]: 2024-04-14 20:50:54 Age [y:d:h:m:s]: 01:207:17:11:48
Block: 1000567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407124 RingCT/type: yes/0
Extra: 017fdb520fc36873b1e8f651ed91f7ccccb6cb6818d3d1501ee10fc73e20c33c220211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44ac3c014b5fc69310e5450189f185df4e19af57f3ddcd8fb1fa312290654c84 0.600000000000 1461065 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": 1000577, "vin": [ { "gen": { "height": 1000567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44ac3c014b5fc69310e5450189f185df4e19af57f3ddcd8fb1fa312290654c84" } } ], "extra": [ 1, 127, 219, 82, 15, 195, 104, 115, 177, 232, 246, 81, 237, 145, 247, 204, 204, 182, 203, 104, 24, 211, 209, 80, 30, 225, 15, 199, 62, 32, 195, 60, 34, 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