Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d42f439c6d2cb9c69a04625f674ccc1d95951336f2554d4cb440d8f56c9ad67

Tx prefix hash: 4280e3cc5ec5ea03d672a478468249846552371bbc96796b9a5b31810c32d419
Tx public key: 7077dd5f65cd6d4987ce725d8f79617219e51ef9c267631d930bdf4f60d32458
Timestamp: 1672598833 Timestamp [UCT]: 2023-01-01 18:47:13 Age [y:d:h:m:s]: 01:335:19:43:55
Block: 665440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501028 RingCT/type: yes/0
Extra: 017077dd5f65cd6d4987ce725d8f79617219e51ef9c267631d930bdf4f60d3245802110000000152542ceb000000000000000000

1 output(s) for total of 3.829314239000 dcy

stealth address amount amount idx
00: 54bb2d74a41ac41becafd7f346ab245c6c28714ab52b1c2dccd754b518577fc3 3.829314239000 1106481 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": 665450, "vin": [ { "gen": { "height": 665440 } } ], "vout": [ { "amount": 3829314239, "target": { "key": "54bb2d74a41ac41becafd7f346ab245c6c28714ab52b1c2dccd754b518577fc3" } } ], "extra": [ 1, 112, 119, 221, 95, 101, 205, 109, 73, 135, 206, 114, 93, 143, 121, 97, 114, 25, 229, 30, 249, 194, 103, 99, 29, 147, 11, 223, 79, 96, 211, 36, 88, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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