Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51d6f80276f63bbb20aa354b11baba98ed62ef0e40e4c46ab6261350006704a3

Tx prefix hash: c2dff8e70d02ced30e7f8a45517a84483688338cbeb97a6a23e23627077080da
Tx public key: 178dff5d45ce2be8b8d294917b4febc1515086d889a295e8b21394c28ca6cab6
Timestamp: 1689521434 Timestamp [UCT]: 2023-07-16 15:30:34 Age [y:d:h:m:s]: 01:227:00:58:37
Block: 805135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423356 RingCT/type: yes/0
Extra: 01178dff5d45ce2be8b8d294917b4febc1515086d889a295e8b21394c28ca6cab602110000000375e3f0e9000000000000000000

1 output(s) for total of 1.319026862000 dcy

stealth address amount amount idx
00: a5d88c3d7b24427feb87a9a308400fce9d9fe2ed0ae1f32ba763495adc34a91b 1.319026862000 1256354 of 0

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": 805145, "vin": [ { "gen": { "height": 805135 } } ], "vout": [ { "amount": 1319026862, "target": { "key": "a5d88c3d7b24427feb87a9a308400fce9d9fe2ed0ae1f32ba763495adc34a91b" } } ], "extra": [ 1, 23, 141, 255, 93, 69, 206, 43, 232, 184, 210, 148, 145, 123, 79, 235, 193, 81, 80, 134, 216, 137, 162, 149, 232, 178, 19, 148, 194, 140, 166, 202, 182, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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