Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435058c9cb6b55780f874059ff307bbf8ea71ef61848351255da4cfeb15ca3d0

Tx prefix hash: 68cf7e350e11427c8e8670b2a336fe974b0b366fe1d00885872c36d7102a5029
Tx public key: 0b023f9c52a1b1f0e2b7ff81c703db72e76e6fd8da0d37d1337e520d250021c4
Timestamp: 1713747426 Timestamp [UCT]: 2024-04-22 00:57:06 Age [y:d:h:m:s]: 01:037:14:48:59
Block: 1005712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287865 RingCT/type: yes/0
Extra: 010b023f9c52a1b1f0e2b7ff81c703db72e76e6fd8da0d37d1337e520d250021c40211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 504c1eea2e3b8f5e412f458a1674d3d944e3a22ff3fad588a36c0f3025be5ef4 0.600000000000 1466496 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": 1005722, "vin": [ { "gen": { "height": 1005712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "504c1eea2e3b8f5e412f458a1674d3d944e3a22ff3fad588a36c0f3025be5ef4" } } ], "extra": [ 1, 11, 2, 63, 156, 82, 161, 177, 240, 226, 183, 255, 129, 199, 3, 219, 114, 231, 110, 111, 216, 218, 13, 55, 209, 51, 126, 82, 13, 37, 0, 33, 196, 2, 17, 0, 0, 0, 7, 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