Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859837440e8e93fafdb55d06b1b0e08c744ff44a12a780db2f58c2c0df046d3e

Tx prefix hash: 24bd6e550c133091120c9b8c7561d87915566eb4dbe9cbfac61e17a2de41464e
Tx public key: a2fcfff6ae1ec2491192df54e605e1fa19882c0870e99cdd5ca3ceeb74218c5b
Timestamp: 1728697245 Timestamp [UCT]: 2024-10-12 01:40:45 Age [y:d:h:m:s]: 00:043:08:52:44
Block: 1129664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30960 RingCT/type: yes/0
Extra: 01a2fcfff6ae1ec2491192df54e605e1fa19882c0870e99cdd5ca3ceeb74218c5b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d30f060f703fbfecc531633617707bcbb0d4c89b2ccdb39961fcf92f1fd5cf3 0.600000000000 1612497 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": 1129674, "vin": [ { "gen": { "height": 1129664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d30f060f703fbfecc531633617707bcbb0d4c89b2ccdb39961fcf92f1fd5cf3" } } ], "extra": [ 1, 162, 252, 255, 246, 174, 30, 194, 73, 17, 146, 223, 84, 230, 5, 225, 250, 25, 136, 44, 8, 112, 233, 156, 221, 92, 163, 206, 235, 116, 33, 140, 91, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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