Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483a6c14d46bde308aabaad13505af2a7218f211e8ffb9120d36fcc160f3e81b

Tx prefix hash: 05653d6661fd7faa8702f8e49eb205eaa96a965c85c6578ead282d3a6ecc6e05
Tx public key: dbce1c59acad8003e369a907beeecd491de4030f3d0f41b5b053e3d7f39b5d09
Timestamp: 1580698669 Timestamp [UCT]: 2020-02-03 02:57:49 Age [y:d:h:m:s]: 04:325:04:50:25
Block: 57565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123768 RingCT/type: yes/0
Extra: 01dbce1c59acad8003e369a907beeecd491de4030f3d0f41b5b053e3d7f39b5d0902110000000417786bcf000000000000000000

1 output(s) for total of 395.642392923000 dcy

stealth address amount amount idx
00: e4c1ef7c0474e7d4ccde54a0367dff98d941bd22491ae5d2925a46ae86f1c86e 395.642392923000 106393 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": 57575, "vin": [ { "gen": { "height": 57565 } } ], "vout": [ { "amount": 395642392923, "target": { "key": "e4c1ef7c0474e7d4ccde54a0367dff98d941bd22491ae5d2925a46ae86f1c86e" } } ], "extra": [ 1, 219, 206, 28, 89, 172, 173, 128, 3, 227, 105, 169, 7, 190, 238, 205, 73, 29, 228, 3, 15, 61, 15, 65, 181, 176, 83, 227, 215, 243, 155, 93, 9, 2, 17, 0, 0, 0, 4, 23, 120, 107, 207, 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