Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ae7fc85a344ed48709c8fae888beb9295f1a183f40e3bdfb9b8ca83a6de316

Tx prefix hash: 6c98c8dcf009e917119f40fdad6ce9ba067e16c4782a1a71d089cf91be1025d0
Tx public key: 267d1e362debe8f671cbd8785b2ee6ac301bf9a1382079f59ab7184852dbe815
Timestamp: 1702200845 Timestamp [UCT]: 2023-12-10 09:34:05 Age [y:d:h:m:s]: 01:116:12:31:16
Block: 909997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344408 RingCT/type: yes/0
Extra: 01267d1e362debe8f671cbd8785b2ee6ac301bf9a1382079f59ab7184852dbe81502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef19c433a76f5a9c83e039fbb2891a014152f6eab8bf82ac86271f80207010b9 0.600000000000 1367136 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": 910007, "vin": [ { "gen": { "height": 909997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef19c433a76f5a9c83e039fbb2891a014152f6eab8bf82ac86271f80207010b9" } } ], "extra": [ 1, 38, 125, 30, 54, 45, 235, 232, 246, 113, 203, 216, 120, 91, 46, 230, 172, 48, 27, 249, 161, 56, 32, 121, 245, 154, 183, 24, 72, 82, 219, 232, 21, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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