Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f625d9741e159967824c25e6f84c3a5e15ad486095aa24c6cd439dd764bcfd

Tx prefix hash: 83495d2734baa9ad352054153a5230730ac854218747cb882d95066dfff467e5
Tx public key: 207afde9b8da048146e28e963767e4d604c6f324a6dd02c7a60e8c898e5b92d2
Timestamp: 1720948565 Timestamp [UCT]: 2024-07-14 09:16:05 Age [y:d:h:m:s]: 00:264:14:33:26
Block: 1065435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189025 RingCT/type: yes/0
Extra: 01207afde9b8da048146e28e963767e4d604c6f324a6dd02c7a60e8c898e5b92d202110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb4c7b9626baab512a6110cfb1302f59b6370e7a92444b728678c41af9f0efee 0.600000000000 1535980 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": 1065445, "vin": [ { "gen": { "height": 1065435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb4c7b9626baab512a6110cfb1302f59b6370e7a92444b728678c41af9f0efee" } } ], "extra": [ 1, 32, 122, 253, 233, 184, 218, 4, 129, 70, 226, 142, 150, 55, 103, 228, 214, 4, 198, 243, 36, 166, 221, 2, 199, 166, 14, 140, 137, 142, 91, 146, 210, 2, 17, 0, 0, 0, 15, 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