Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d4b55ff9e59a0a99caf04cd920aca0953da501db49f5e9197ce92c6ca10909

Tx prefix hash: ffa61b5a3c44ade6a40dbe8e169d4803f156cd12fb568915a008221e58c121fc
Tx public key: f4af4cc101b1923459a5b750c77ad687998a1ba7c9972d97ba6a10b8abe7d3e0
Timestamp: 1696719162 Timestamp [UCT]: 2023-10-07 22:52:42 Age [y:d:h:m:s]: 01:208:03:29:56
Block: 864755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409817 RingCT/type: yes/0
Extra: 01f4af4cc101b1923459a5b750c77ad687998a1ba7c9972d97ba6a10b8abe7d3e002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.836965859000 dcy

stealth address amount amount idx
00: 4929bf38b55498e0247a216b5b0b671fa53e8236802f310ba16475ea1fb714bf 0.836965859000 1319275 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": 864765, "vin": [ { "gen": { "height": 864755 } } ], "vout": [ { "amount": 836965859, "target": { "key": "4929bf38b55498e0247a216b5b0b671fa53e8236802f310ba16475ea1fb714bf" } } ], "extra": [ 1, 244, 175, 76, 193, 1, 177, 146, 52, 89, 165, 183, 80, 199, 122, 214, 135, 153, 138, 27, 167, 201, 151, 45, 151, 186, 106, 16, 184, 171, 231, 211, 224, 2, 17, 0, 0, 0, 4, 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