Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675b79b25f3c5269540bf9ebbd091a7a2b7a0df0ba7af6426db8c12c0b7bf919

Tx prefix hash: b7f83e34164a4a46b57eddaf8112ec5bbca8a96d85f2c412e087e020c5d4822b
Tx public key: 218d23948cd9a2e21aec0b4c7266bc26c9799aa3e3a42f43d235ecb2ddcef95b
Timestamp: 1700246666 Timestamp [UCT]: 2023-11-17 18:44:26 Age [y:d:h:m:s]: 01:354:07:06:27
Block: 893794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512087 RingCT/type: yes/0
Extra: 01218d23948cd9a2e21aec0b4c7266bc26c9799aa3e3a42f43d235ecb2ddcef95b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.670639978000 dcy

stealth address amount amount idx
00: 3b20bc35b63ff9868160df4772a22766779ad69622ab1e9ef70025f9b682a78b 0.670639978000 1349979 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": 893804, "vin": [ { "gen": { "height": 893794 } } ], "vout": [ { "amount": 670639978, "target": { "key": "3b20bc35b63ff9868160df4772a22766779ad69622ab1e9ef70025f9b682a78b" } } ], "extra": [ 1, 33, 141, 35, 148, 140, 217, 162, 226, 26, 236, 11, 76, 114, 102, 188, 38, 201, 121, 154, 163, 227, 164, 47, 67, 210, 53, 236, 178, 221, 206, 249, 91, 2, 17, 0, 0, 0, 1, 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