Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23dbeb59d53ea26ab53a8525632bf8edbd5c764f3e985c879654a0176e49c69f

Tx prefix hash: d2fca21a3a7173048f7b82d071180f63bd358bd2488fbf1c404275067231a6cd
Tx public key: 6b3127ada106f321abcc92341d8aaf523eac748a8ec8a7c7d361cb9110fb827e
Timestamp: 1733831073 Timestamp [UCT]: 2024-12-10 11:44:33 Age [y:d:h:m:s]: 00:138:22:15:32
Block: 1172128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99097 RingCT/type: yes/0
Extra: 016b3127ada106f321abcc92341d8aaf523eac748a8ec8a7c7d361cb9110fb827e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa1058f8f08d4eca4b699742782614e39ac1b8b269d1b89e64be2eff6ca36bb4 0.600000000000 1657979 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": 1172138, "vin": [ { "gen": { "height": 1172128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa1058f8f08d4eca4b699742782614e39ac1b8b269d1b89e64be2eff6ca36bb4" } } ], "extra": [ 1, 107, 49, 39, 173, 161, 6, 243, 33, 171, 204, 146, 52, 29, 138, 175, 82, 62, 172, 116, 138, 142, 200, 167, 199, 211, 97, 203, 145, 16, 251, 130, 126, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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