Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d3cda26ab08d8da5295f4bb50c5f2926235ab4178b429f0647a0c28b3c1ebf

Tx prefix hash: 34841a092ff5b4ffbf338d6ceb756037c9b46bec38e53460db9ddde62eb791b8
Tx public key: 7c33e05dfa7c9f55b30f4eda6e4771c629ee7e9e6d2fac9092dec9d206ecb83c
Timestamp: 1703452246 Timestamp [UCT]: 2023-12-24 21:10:46 Age [y:d:h:m:s]: 01:081:06:46:54
Block: 920364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319212 RingCT/type: yes/0
Extra: 017c33e05dfa7c9f55b30f4eda6e4771c629ee7e9e6d2fac9092dec9d206ecb83c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dee6f318d640196fc061f0236964f9593e3016c6e0351b3f885026eb1600951 0.600000000000 1378042 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": 920374, "vin": [ { "gen": { "height": 920364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dee6f318d640196fc061f0236964f9593e3016c6e0351b3f885026eb1600951" } } ], "extra": [ 1, 124, 51, 224, 93, 250, 124, 159, 85, 179, 15, 78, 218, 110, 71, 113, 198, 41, 238, 126, 158, 109, 47, 172, 144, 146, 222, 201, 210, 6, 236, 184, 60, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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