Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5c8463dd5c8fb2ce2216496f9c626daf214fa9acbd978307e7b020038dfe87

Tx prefix hash: be58130cbe2b62ebe372002ed477bc05ebd49d5d9d0e544d6bea65fa9b624b68
Tx public key: a63daf017eaea547929cf59f6e46b35678b7cc59b4f729969989218b8483c38c
Timestamp: 1735173028 Timestamp [UCT]: 2024-12-26 00:30:28 Age [y:d:h:m:s]: 00:090:11:01:31
Block: 1183228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64412 RingCT/type: yes/0
Extra: 01a63daf017eaea547929cf59f6e46b35678b7cc59b4f729969989218b8483c38c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f04f652d16f6e54d75a5e52036d4394d3585417a54c473cbbb98756d7c23aac 0.600000000000 1669669 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": 1183238, "vin": [ { "gen": { "height": 1183228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f04f652d16f6e54d75a5e52036d4394d3585417a54c473cbbb98756d7c23aac" } } ], "extra": [ 1, 166, 61, 175, 1, 126, 174, 165, 71, 146, 156, 245, 159, 110, 70, 179, 86, 120, 183, 204, 89, 180, 247, 41, 150, 153, 137, 33, 139, 132, 131, 195, 140, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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