Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea3f7f325b144d3428791cef6e7c45cfaeb404a8f8b8291fd40ec18a02bd22e

Tx prefix hash: 495ecfb65377075a5adad17512eb3f31156d7a717e8a59d8543f969e703470fa
Tx public key: c25da6e6d3b3d209f4b68258f39ca077bc2e328b652188c852d52178c4091e00
Timestamp: 1716320592 Timestamp [UCT]: 2024-05-21 19:43:12 Age [y:d:h:m:s]: 00:281:20:33:25
Block: 1027055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201425 RingCT/type: yes/0
Extra: 01c25da6e6d3b3d209f4b68258f39ca077bc2e328b652188c852d52178c4091e000211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f2d6ec37b9758163ccf519ae5dfb947c2ee29470dfccf9963cb471649844d0 0.600000000000 1494478 of 15

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": 1027065, "vin": [ { "gen": { "height": 1027055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f2d6ec37b9758163ccf519ae5dfb947c2ee29470dfccf9963cb471649844d0" } } ], "extra": [ 1, 194, 93, 166, 230, 211, 179, 210, 9, 244, 182, 130, 88, 243, 156, 160, 119, 188, 46, 50, 139, 101, 33, 136, 200, 82, 213, 33, 120, 196, 9, 30, 0, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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