Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa98e537ed46e16053f7a11e4dd681e619f9acdc49548d77824fde7a1738ca3c

Tx prefix hash: 35081605b7cf44a279d914d8f6409eaa1329c30ae8737c2c6816d090180320aa
Tx public key: c71a185df06ec86cf5592e4fb4e45b73072df7e5388c2bf80707dcea20737e7c
Timestamp: 1727417972 Timestamp [UCT]: 2024-09-27 06:19:32 Age [y:d:h:m:s]: 00:117:20:00:51
Block: 1119064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84198 RingCT/type: yes/0
Extra: 01c71a185df06ec86cf5592e4fb4e45b73072df7e5388c2bf80707dcea20737e7c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d6ff3abc6af051f636017ebaf0f17367293ffd40af6dd79d1e08ea1c2ed08dd 0.600000000000 1600479 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": 1119074, "vin": [ { "gen": { "height": 1119064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d6ff3abc6af051f636017ebaf0f17367293ffd40af6dd79d1e08ea1c2ed08dd" } } ], "extra": [ 1, 199, 26, 24, 93, 240, 110, 200, 108, 245, 89, 46, 79, 180, 228, 91, 115, 7, 45, 247, 229, 56, 140, 43, 248, 7, 7, 220, 234, 32, 115, 126, 124, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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