Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf808c6e9edbc07c1a96dbbd6c5288501620161974ac24304af257401d01e8c

Tx prefix hash: 754a37e13fcba5cb894b56ebc9638ab4ecc6069146769a0738483b9ba2e5ec59
Tx public key: d6416ec3966ff3fd63ba5f3834ebef28fd1d61495dd100c62196f3e8c8aea83d
Timestamp: 1576643462 Timestamp [UCT]: 2019-12-18 04:31:02 Age [y:d:h:m:s]: 04:344:06:26:09
Block: 28232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133119 RingCT/type: yes/0
Extra: 01d6416ec3966ff3fd63ba5f3834ebef28fd1d61495dd100c62196f3e8c8aea83d0211000000459159db1e000000000000000000

1 output(s) for total of 494.830578284000 dcy

stealth address amount amount idx
00: 55ff832801a5949a89717eac3e2280bb4b6dcfea2fbad7d9e99f94ed644fb204 494.830578284000 46762 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": 28242, "vin": [ { "gen": { "height": 28232 } } ], "vout": [ { "amount": 494830578284, "target": { "key": "55ff832801a5949a89717eac3e2280bb4b6dcfea2fbad7d9e99f94ed644fb204" } } ], "extra": [ 1, 214, 65, 110, 195, 150, 111, 243, 253, 99, 186, 95, 56, 52, 235, 239, 40, 253, 29, 97, 73, 93, 209, 0, 198, 33, 150, 243, 232, 200, 174, 168, 61, 2, 17, 0, 0, 0, 69, 145, 89, 219, 30, 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