Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fabc149375f68e097bdf053c097d4038309d30cf24a1bf6714f8359e3a88688a

Tx prefix hash: c61a496395a5c331b237935a9465c5721f9afafcd731e2964f803e086e1b0a7f
Tx public key: 732922480b29fbf84aa13b4b4731b0527a1d6db1419f18d72f2cbb3da4515b0b
Timestamp: 1694935497 Timestamp [UCT]: 2023-09-17 07:24:57 Age [y:d:h:m:s]: 01:164:12:20:08
Block: 849943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378636 RingCT/type: yes/0
Extra: 01732922480b29fbf84aa13b4b4731b0527a1d6db1419f18d72f2cbb3da4515b0b021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.937100284000 dcy

stealth address amount amount idx
00: 5e431045df743e7ae61f40789357a5a8ec8c918e8b53256287b2f8b19cff96f3 0.937100284000 1303633 of 0

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": 849953, "vin": [ { "gen": { "height": 849943 } } ], "vout": [ { "amount": 937100284, "target": { "key": "5e431045df743e7ae61f40789357a5a8ec8c918e8b53256287b2f8b19cff96f3" } } ], "extra": [ 1, 115, 41, 34, 72, 11, 41, 251, 248, 74, 161, 59, 75, 71, 49, 176, 82, 122, 29, 109, 177, 65, 159, 24, 215, 47, 44, 187, 61, 164, 81, 91, 11, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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