Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4f7e4df1fc62d77b4dc3ce57be87f7ec4ee0ef42040b9026a373e721bfcc9f5

Tx prefix hash: 30637211772eaa7dbf0ebdf6e0824ea9b64e9b5df0e5152c0d806f7b68614870
Tx public key: b3eabbadf6e2e5835fbc2ea2ceb3517c11f61381575347ec5dbcb8db7f9fd77a
Timestamp: 1737663335 Timestamp [UCT]: 2025-01-23 20:15:35 Age [y:d:h:m:s]: 00:293:15:05:51
Block: 1203788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207409 RingCT/type: yes/0
Extra: 01b3eabbadf6e2e5835fbc2ea2ceb3517c11f61381575347ec5dbcb8db7f9fd77a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 854f918c002cd54d8bc8272a22f82334205d8a79da6de777b5ec9f6d63b75dc3 0.600000000000 1690467 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": 1203798, "vin": [ { "gen": { "height": 1203788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "854f918c002cd54d8bc8272a22f82334205d8a79da6de777b5ec9f6d63b75dc3" } } ], "extra": [ 1, 179, 234, 187, 173, 246, 226, 229, 131, 95, 188, 46, 162, 206, 179, 81, 124, 17, 246, 19, 129, 87, 83, 71, 236, 93, 188, 184, 219, 127, 159, 215, 122, 2, 17, 0, 0, 0, 7, 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