Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa087c88bc5eaecd2dc33fdf4bfbbd6bb8ef41bd8f5f7bec287985a16037965

Tx prefix hash: d9f0a4062d0db7089999df52db697bffdd30ea58e9c61dd7e95748066af41239
Tx public key: fd8f0eee4bb6fe88f2f7c8bb460a7ce35c6f27ce9649941557bf1390ebc08c3e
Timestamp: 1731277025 Timestamp [UCT]: 2024-11-10 22:17:05 Age [y:d:h:m:s]: 00:013:15:43:04
Block: 1150961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9774 RingCT/type: yes/0
Extra: 01fd8f0eee4bb6fe88f2f7c8bb460a7ce35c6f27ce9649941557bf1390ebc08c3e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7e977269491c3249a23ed115c301408e680dbe114660f687e1fd029b196d136 0.600000000000 1636404 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": 1150971, "vin": [ { "gen": { "height": 1150961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7e977269491c3249a23ed115c301408e680dbe114660f687e1fd029b196d136" } } ], "extra": [ 1, 253, 143, 14, 238, 75, 182, 254, 136, 242, 247, 200, 187, 70, 10, 124, 227, 92, 111, 39, 206, 150, 73, 148, 21, 87, 191, 19, 144, 235, 192, 140, 62, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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