Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a13e117e133137f71386c6a679bf7ff94f376996f6ceb5a6ff4ef17a41de7c0

Tx prefix hash: 36c5d8091fec2dad4c009d1f7a46921850407e272b058b00831645da41f40281
Tx public key: d5ef07f9b8ac324ac7447515d5a5c8b81aad4bf4dbc7dad94b02e17742f4d850
Timestamp: 1711906536 Timestamp [UCT]: 2024-03-31 17:35:36 Age [y:d:h:m:s]: 01:227:13:35:49
Block: 990471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421321 RingCT/type: yes/0
Extra: 01d5ef07f9b8ac324ac7447515d5a5c8b81aad4bf4dbc7dad94b02e17742f4d850021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e98aaadcb164d5405e66e3ae6afe28eebd4c9940f7730e9f873f852c3bc85dc 0.600000000000 1450793 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": 990481, "vin": [ { "gen": { "height": 990471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e98aaadcb164d5405e66e3ae6afe28eebd4c9940f7730e9f873f852c3bc85dc" } } ], "extra": [ 1, 213, 239, 7, 249, 184, 172, 50, 74, 199, 68, 117, 21, 213, 165, 200, 184, 26, 173, 75, 244, 219, 199, 218, 217, 75, 2, 225, 119, 66, 244, 216, 80, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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