Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f36af4aa8eedd76e95ce07cb6232591674f5959dcbdaefe1448bd2bb2fef84

Tx prefix hash: 98dba291ec9c3a25eb31d4ca731e3a073172a8e271791b6e92fd80e90b1f3da7
Tx public key: 43e50be39ef52ec71df915d90b04c253dff006b5bf4644d994d3c750d15ceb9c
Timestamp: 1737562175 Timestamp [UCT]: 2025-01-22 16:09:35 Age [y:d:h:m:s]: 00:147:19:57:52
Block: 1202960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105372 RingCT/type: yes/0
Extra: 0143e50be39ef52ec71df915d90b04c253dff006b5bf4644d994d3c750d15ceb9c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d436a11a96c7fbc3ff488e32fa1dccb76947c5110bed8559557cd8d6ae3783a 0.600000000000 1689627 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": 1202970, "vin": [ { "gen": { "height": 1202960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d436a11a96c7fbc3ff488e32fa1dccb76947c5110bed8559557cd8d6ae3783a" } } ], "extra": [ 1, 67, 229, 11, 227, 158, 245, 46, 199, 29, 249, 21, 217, 11, 4, 194, 83, 223, 240, 6, 181, 191, 70, 68, 217, 148, 211, 199, 80, 209, 92, 235, 156, 2, 17, 0, 0, 0, 2, 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