Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95c351c3e03cf79a046d25130055e1467c71c83153a4e22ff68f9b5854ec512

Tx prefix hash: 1793e204670c5617a101f340d93af9ab70971e140dcf4c2e119d21079e080622
Tx public key: ea7a2b00c91b6ffc3ac928576bbb835d9fd05621adc838446000a705cdd1beae
Timestamp: 1728658697 Timestamp [UCT]: 2024-10-11 14:58:17 Age [y:d:h:m:s]: 00:179:17:26:04
Block: 1129337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128242 RingCT/type: yes/0
Extra: 01ea7a2b00c91b6ffc3ac928576bbb835d9fd05621adc838446000a705cdd1beae021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77f78cb32255832ca34f3e79cb4c9243c0abdc36dd0f1d9b623d0a2163e2ae2e 0.600000000000 1612162 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": 1129347, "vin": [ { "gen": { "height": 1129337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77f78cb32255832ca34f3e79cb4c9243c0abdc36dd0f1d9b623d0a2163e2ae2e" } } ], "extra": [ 1, 234, 122, 43, 0, 201, 27, 111, 252, 58, 201, 40, 87, 107, 187, 131, 93, 159, 208, 86, 33, 173, 200, 56, 68, 96, 0, 167, 5, 205, 209, 190, 174, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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